Repository navigation
Conversation
Auto-detects runit at runtime via /run/runit and sv; queries all services in one sv status call and maps runit states to the existing Service model fields. Systemd remains the primary backend; runit is tried when systemd is absent. No configuration required. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Hello, I don't really mind if you used AI for this as long as you understand the change thoroughly and it was well tested. Did you test it? Does it work there? For me there are 2 problems - I don't know much about runit, I will install void linux into VM to test it out eventually, but unless this was well tested at least by you, then that's a blocker. Second problem is that it seems to rely on execution of external command. I have that systemctl call as a workaround and actually should probably remove it (by default we use libsystemd.so and direct calls) - executing external commands repeatedly in a loop is problematic and in my opinion unclean design (it also complicates debugging sessions). Does runit provide some other interface? Like some dynamically linked libraries we cloud load instead? |
|
Hi Petr Runit is just interactions with files in Here's an explanation:
supervise/ (and log/supervise/) These are not user-created or user-edited; runsv owns them. I completely understand your problem! and won't mind at all if you just close this PR. I just want to comment that your codebase is really clean, which is why it was so simple to add the runit interaction. |
|
Petr, thanks for your feedback and the cool tool you made. It's too much work for you to maintain this capability, on a system that you don't use, and most of the Void users are hard-core command line junkies anyway :-) So I'm withdrawing the PR. Greetings. |
Based on this reddit conversation I've added
runitsupport (being used in Void linux) to the Services tab. It was mostly a Claude testcase for me, and I found the resulting code very clean.Feel free to just ignore this PR!!! However if you decide to merge, I'll need to add some information to the readme, because by default on Void, one needs to be
rootin order to read the statuses of the services. The solution I wrote in the reddit thread I mentioned above.Auto-detects runit at runtime via /run/runit and sv; queries all services in one sv status call and maps runit states to the existing Service model fields. Systemd remains the primary backend; runit is tried when systemd is absent. No configuration required.